In the last, the system is described as a collection of modules or subsystems. In this stage, modular and subsystems programming code will take effect, and then the individual modules will be tested before they are integrated in the next level. The code is tested and retested at various levels; system, unit, and user acceptance testing are often performed depending on the consultant's judgment and this is something that is repeatedly discussed with organization and stakeholders. The amount of testing, therefore, depends on the particular organization. The consultant has to know when to cease analysis.

The final stage -- instillation, implementation or deployment is when the software is put into production and actually used by the organization.

Maintenance will take place on a regular level. This is particularly so since changes of personnel in the organization (new ones entering, certain others leaving) as, so too, constant flow of data change will necessitate constant system update.

(n.d.). Introduction to Relational Databases - Part 1: Theoretical Foundation. 15 seconds. Retrieved on 7/31/2011from: http://www.15seconds.com/issue/020522.htm
Davidson, L. (2007). Ten Common Database Design Mistakes. Simple Talk. Retrieved on 7/31/2011from: http://www.simple-talk.com/sql/database-administration/ten-common-database-design-mistakes/References

MKS Software Development Life Cycle (SDLC) / System Development

http://www.mks.com/resources/resource-pages/software-development-life-cycle-sdlc-system-development

SaaSSDLC.com -- Systems Engineering and Software Development Life Cycle Framework

http://opensdlc.org/mediawiki/index.php?title=Main_Page

SDLC Definition. Retrieved on 7/31/2011from:

sdlcproject.com/2011/01/21/sdlc-requirements-definition

Styluinc. Software Development Life Cycle (SDLC) http://www.stylusinc.com/Common/Concerns/SoftwareDevtPhilosophy.php